FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.ehrsfmr21#current (31 ms)

Package hl7.ehrs.ehrsfmr21
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-RI.1.1.13.html
Url http://hl7.org/ehrs/Requirements/EHRSFMR2.1-RI.1.1.13
Version 2.1.0
Status active
Date 2024-11-26T16:30:50+00:00
Name RI_1_1_13_Extract_Record_Lifecycle_Event
Title RI.1.1.13 Extract Record Lifecycle Event (Function)
Experimental False
Realm uv
Authority hl7
Description Extract Record Entry content to produce subsets, derivations or aggregations (1 or more instances)
Purpose Occurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria. Reference: ISO 21089-2018, Section 15.13.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Extract Record Entry content to produce subsets, derivations or aggregations (1 or more instances)

Description I:

Occurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria.

Reference: ISO 21089-2018, Section 15.13.

Criteria N:
RI.1.1.13#01 dependent SHALL

The system SHALL provide the ability to extract Record Entry content to produce subsets, derivations, summaries or aggregations according to scope of practice, organizational policy, and/or jurisdictional law.

RI.1.1.13#02 SHALL

The system SHALL provide the ability to de-identify Record Entries during extraction in accordance with function [[RI.1.1.10]] (De-Identify Record Entries).

RI.1.1.13#03 SHALL

The system SHALL provide the ability to extract Record Entry content based on queries with selection criteria, for example, key words, date/time range, full text search.

RI.1.1.13#04 SHALL

The system SHALL provide the ability to extract metadata associated with Record Entry content.

RI.1.1.13#05 SHOULD

The system SHOULD provide the ability to extract, with parameterized selection criteria, across the complete data set that constitutes all Record Entries for a patient.

RI.1.1.13#06 SHOULD

The system SHOULD provide the ability to extract and present a full chronicle of the healthcare process from assembled Record Entries.

RI.1.1.13#07 SHOULD

The system SHOULD provide the ability to extract and present a full chronicle of healthcare delivered to a patient from assembled Record Entries.

RI.1.1.13#08 SHALL

The system SHALL provide the ability to extract Record Entry content for various purposes, including administrative, financial, research, quality analysis and public health.

RI.1.1.13#09 SHOULD

The system SHOULD provide the ability to extract Record Entries for system migration.

RI.1.1.13#10 SHOULD

The system SHOULD provide the ability to manage a set of over-riding parameters to exclude sensitive or privileged Record Entry content from extraction.

RI.1.1.13#11 MAY

The system MAY provide the ability to extract unstructured Record Entry content and convert it into structured data.


Source

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-RI.1.1.13",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Extract Record Entry content to produce subsets, derivations or aggregations (1 or more instances)</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Occurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria.</p>\n<p>Reference: ISO 21089-2018, Section 15.13.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to extract Record Entry content to produce subsets, derivations, summaries or aggregations according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to de-identify Record Entries during extraction in accordance with function [[RI.1.1.10]] (De-Identify Record Entries).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to extract Record Entry content based on queries with selection criteria, for example, key words, date/time range, full text search.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to extract metadata associated with Record Entry content.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to extract, with parameterized selection criteria, across the complete data set that constitutes all Record Entries for a patient.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to extract and present a full chronicle of the healthcare process from assembled Record Entries.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to extract and present a full chronicle of healthcare delivered to a patient from assembled Record Entries.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to extract Record Entry content for various purposes, including administrative, financial, research, quality analysis and public health.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to extract Record Entries for system migration.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage a set of over-riding parameters to exclude sensitive or privileged Record Entry content from extraction.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.1.13#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to extract unstructured Record Entry content and convert it into structured data.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-RI.1.1.13",
  "version" : "2.1.0",
  "name" : "RI_1_1_13_Extract_Record_Lifecycle_Event",
  "title" : "RI.1.1.13 Extract Record Lifecycle Event (Function)",
  "status" : "active",
  "date" : "2024-11-26T16:30:50+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Extract Record Entry content to produce subsets, derivations or aggregations (1 or more instances)",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "purpose" : "Occurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria. \n\nReference: ISO 21089-2018, Section 15.13.",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-01",
      "label" : "RI.1.1.13#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to extract Record Entry content to produce subsets, derivations, summaries or aggregations according to scope of practice, organizational policy, and/or jurisdictional law."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-02",
      "label" : "RI.1.1.13#02",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to de-identify Record Entries during extraction in accordance with function [[RI.1.1.10]] (De-Identify Record Entries)."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-03",
      "label" : "RI.1.1.13#03",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to extract Record Entry content based on queries with selection criteria, for example, key words, date/time range, full text search."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-04",
      "label" : "RI.1.1.13#04",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to extract metadata associated with Record Entry content."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-05",
      "label" : "RI.1.1.13#05",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to extract, with parameterized selection criteria, across the complete data set that constitutes all Record Entries for a patient.",
      "derivedFrom" : "EHR-S_FM_R1.1 IN.2.4#5"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-06",
      "label" : "RI.1.1.13#06",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to extract and present a full chronicle of the healthcare process from assembled Record Entries.",
      "derivedFrom" : "EHR-S_FM_R1.1 IN.2.4#6"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-07",
      "label" : "RI.1.1.13#07",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to extract and present a full chronicle of healthcare delivered to a patient from assembled Record Entries."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-08",
      "label" : "RI.1.1.13#08",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : false,
      "requirement" : "The system SHALL provide the ability to extract Record Entry content for various purposes, including administrative, financial, research, quality analysis and public health.",
      "derivedFrom" : "EHR-S_FM_R1.1 DC.1#11"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-09",
      "label" : "RI.1.1.13#09",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to extract Record Entries for system migration."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-10",
      "label" : "RI.1.1.13#10",
      "conformance" : [
        "SHOULD"
      ],
      "conditionality" : false,
      "requirement" : "The system SHOULD provide the ability to manage a set of over-riding parameters to exclude sensitive or privileged Record Entry content from extraction."
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : false
        }
      ],
      "key" : "EHRSFMR2.1-RI.1.1.13-11",
      "label" : "RI.1.1.13#11",
      "conformance" : [
        "MAY"
      ],
      "conditionality" : false,
      "requirement" : "The system MAY provide the ability to extract unstructured Record Entry content and convert it into structured data."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.